Troubleshooting CygNet Measurement

The following tips might be helpful in solving issues that may arise using CygNet Measurement.

• Initial device configuration errors
• Start-up errors: Installation
• Start-up errors: Workspace
• GMR to FMS migration errors
• Slow FMS service
• Replication errors
• Configuration data group poll fails
• Group configuration error message appears
• Invalid data is returned; record is skipped
• Data fails to be published to SCADA
• Node disappears from Node Chooser list

Initial Device Configuration Errors

It is helpful to ensure that your devices are configured properly before beginning to use CygNet Measurement, since various devices and calculation types have specific configuration data requirements to function successfully in the system.

See Configuring Remote Devices for CygNet Measurement and Required Device Configuration Data for CygNet Measurement for more information.

Start-up Errors: Installation

The following table provides details about common start-up errors that may be encountered while installing CygNet measurement. This information is meant to help you troubleshoot errors in your installation.

Error	Notes
ERROR::A compatible version of the calculation engine library cannot be loaded, Exiting...	Confirm you have installed the proper calculation engine (CygMeasCalc.dll).
ERROR::A compatible version of the validation engine library cannot be loaded, Exiting...	Confirm you have installed the proper validation engine (FmsValidationEngine.dll).
ERROR::Unable to load the time zone file from the ARS, Exiting...	Confirm you have installed the proper time zone file (CygNetTimeZones.xml). See CygNetTimeZones.xml File for more information.
ERROR::The time zone file does not contain any valid entries, Exiting...	Confirm your installed time zone file (CygNetTimeZones.xml) is properly defined. See CygNetTimeZones.xml File for more information.
Invalid licensing for Measurement System (FMS), Exiting...	Confirm you have installed the proper CygNet Measurement license file (CygNet.lic). Confirm it is in the correct location (CygNet\Services\ARS). See Licensing Requirements for more information.

Start-up Errors: Workspace

When FMS Explorer initially opens, a Workspace (.few) file optionally provides the previously saved options, controls, reports, commands, session settings, etc. to your client machine. How the Workspace file is saved and loaded each time the client opens/closes is as configured on the File menu, where you can determine how you want to pick up your work environment when you next come back to it. See Managing Workspaces for more information.

• If your workspace does not appear as expected, first check your workspace settings as configured on the File menu and verify that the settings are configured and saved as desired.
• If your workspace will not load at all, or if the file seems to be corrupted, you may need to override the auto-load setting in order to launch a new workspace.

  If necessary, you can override the setting and start anew by using the following command-line parameter:

  /noload

  Warning:
  Using this override can overwrite your existing workspace file and lose all information saved therein, depending on the workspace file settings saved on the File menu.

  See Managing Workspaces for more information.

GMR to FMS Migration Errors

If a large number of errors occur while using FMS Toolbox to migrate files from a GMR to an FMS system, the most common cause is the integrity of your GMR configuration data. Whereas GMR was able to store data independent of its configuration data, FMS performs a broad array of data calculations that require valid configuration values. When required configuration values are missing or out of range, the system will generate error messages.

See Required Device Configuration Data for CygNet Measurement for more information.

Slow FMS Service

If the FMS service seems to have slowed, one possibility to consider is that database indexes have become fragmented. In any event, it is highly recommended that database administrators regularly perform an index rebuild, as a component of a regularly scheduled database maintenance protocol, to maximize performance.

Replication Errors

Error Message

Description

Unable to execute the IDENTITY_INSERT statement.  Check Permissions.

This indicates a database error that occurs when attempting to set an IDENTITY_INSERT at runtime. The error message could appear when trying to start an FMS after setting up FMS replication, and could be caused by a problem with permissions for Microsoft SQL Server tables. Check permissions in the user account associated with your FMS. Microsoft states: “User must own the table or have ALTER permission on the table.” Refer to Microsoft online documentation for more information.

Configuration Data Group Poll Fails

If a Request Current Configuration poll is not successful, there could be unsupported inputs in the configuration of the remote device. When this is the case, an error will be logged to the command log, where you can view details of the error, e.g. "Invalid value for eFMS_CFG_..." or "Unsupported meter type...."

See Viewing Command Logs for more information.

Group Configuration Error Message Appears

If an error message is generated while you are creating a group, the membership requirement that failed and the reason for the failure will be reported in the message. Group Node membership follows specific sets of membership requirements according to group type.

See Group Node Membership Requirements for more information.

The following error messages can be generated.

Error Code	Message	Group Type(s)	Description
20000	Node does not exist.	All	The Node being added can't be added to a group before or after the group exists. The Node being added can't be added to a group before or after the Node exists.
20072	A General Group with a defined uniqueness type can't contain other groups.	General Groups: Unique	If it's a unique group, it can only contain devices.
20073	A group can't be recursive.	All	You can't place a group into another group if it will create a recursive loop.
20074	A Node cannot be a member of multiple groups using the same uniqueness type.	General Groups: Unique	Each member device can only be in a single group of each unique type at any given time.
20075	Virtual Station groups can only contain stations or liquid devices.	Station Groups: Virtual	The group can contain other stations (virtual or physical) or liquid devices.
20076	Physical Station groups can only contain gas devices.	Station Groups: Physical	The group can only contain gas meter devices (not chromatographs or station meters, which are gas meters set to also function as stations).
20080	A Station's entries can't be changed during a period when it is closed.	Station Groups: Physical	You can't add a device into a station if the station was closed during some portion of the time during which the device is being added. You can't remove a device from a station if the station was closed during some portion of the time during which the device is being removed.
20083	A Device can only be in one Station.	Station Groups: Physical	Devices can only exist in a single Station group at any given time.

Invalid Data is Returned; Record is Skipped

If invalid data is returned from an EIE or a data file, no transaction record will be generated for the poll, making it appear as though the record was "skipped" in the results. If an invalid enumeration item value (e.g. plate material of zero) is detected, the FMS will generate an exception. No raw or normalized configuration log entry will be processed. In other situations, such as an invalid timestamp, an error will be written to the command log. Some possible reasons for skipped records due to invalid data are listed in the following table.

Problem	Notes
Skipped records	Command parameter values may not be within valid ranges for the request. To confirm, check the command log error messages.
	Data timestamp values may not be within the valid range for the request, or for the Node. To confirm, check the command log for error messages.
	Valid, non-zero timestamps may not be present where time entry is required. To confirm, check the command log for error messages.
	The device might be returning values for both IV and Linear IV. Only one of these values can be processed for a transaction. To confirm, check the device template file.

Data Fails to be Published to the SCADA System

If data fails to be published to the VHS in the SCADA system, check the security application for the FMS. The FMS needs appropriate security permission to make updates to the UIS and the VHS, so that data being published to the SCADA system via normalization views will not fail due to security restrictions. See the following topics for more information.

• Installing CygNet Measurement (step 3. Install the Flow Measurement Service (FMS))
• Normalization Views and Security
• FMS Security
• Implementing Security

Node Disappears from Node Chooser List

If a Node that previously appeared in your Node Chooser no longer appears in the Node list, consider the following possibilities.

• A filtering component was changed - check your filtering components and retrieve Nodes again
• The Node was purged from the system - it will no longer appear in any Node Chooser
• The Node was deleted from a Point in Time, so it no longer exists indefinitely in the system - try looking at your system from the perspective of a time at which you know the Node existed. To do this, specify a Point in Time on the Home menu. See Using the Home Menu for more information.